Processing alarm signals

ABSTRACT

Methods, systems, computer-readable media, and apparatuses for processing alarm signals are presented. In some embodiments, a mobile device may be registered with a security system that is installed at a premises. Subsequently, an alarm trigger associated with the security system may be received. Based on receiving the alarm trigger, the location of the mobile device may be determined. A response to the alarm trigger then may be determined based on the location of the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/281,596, filed Feb. 21, 2019, which is a continuation of U.S. patentapplication Ser. No. 15/658,720, filed Jul. 25, 2017, now U.S. Pat. No.10,262,526, issued Apr. 16, 2019, which is a continuation of U.S. patentapplication Ser. No. 14/687,122, filed Apr. 15, 2015, now U.S. Pat. No.9,754,477, issued Sep. 5, 2017, which is a continuation of U.S. patentapplication Ser. No. 13/826,489, filed Mar. 14, 2013, now U.S. Pat. No.9,035,763, issued May 19, 2015, each of which is incorporated herein, byreference, in its entirety.

BACKGROUND

Aspects of the disclosure relate to hardware and computer software thatmay be used with or implemented by home security systems. In particular,various aspects of the disclosure relate to processing alarm signals,such as alarm signals that may be generated and/or received by a homesecurity console or other security system controller device from one ormore sensors installed at a premises.

Increasingly, houses, apartments, offices, and other premises are beingsecured with home security systems, which are also sometimes referred toas “burglar alarms.” In addition to providing those who live and work inthese places with a sense of security and greater peace of mind, manysecurity systems are also beginning to provide users with a number ofother beneficial features, such as the ability to remotely control andmonitor a security system even when away from the monitored premises.

Despite advances in technology, however, false alarms continue to be anissue that can frustrate users of security systems. For example, notonly can false alarms be a nuisance as a result of the unwanted noise,light, and attention that may accompany them, but false alarms can alsohave legal and financial consequences. For instance, some municipalitiesmay impose fines and other penalties on homeowners if emergencyresponders (e.g., police units, fire units, ambulances, etc.) aredispatched in response to a false alarm at a home. There remains anever-present need to minimize resources wasted on false alarms, and toimprove efficiency of home security systems.

BRIEF SUMMARY

Aspects of the disclosure provide more effective ways of reducing falsealarms by a security system, as well as more convenient and easy-to-useways of managing a security system, such as a home security system.

In particular, various techniques are discussed below that enable analarm to be automatically deactivated in certain circumstances in whichthe alarm is most likely to be a false alarm. One way in which some ofthe systems and methods discussed below can identify a false alarm is todetermine and evaluate the locations of different mobile devices thatbelong to different people who reside or work at the premises where thealarm was triggered. Based on where particular mobile devices arelocated, conclusions can be reached about where the users of thesedevices are located and the veracity of an alarm can be determined.

Some embodiments discussed below also provide a number of additional andalternative features. For example, in some embodiments, an alarm may beverified by contacting one or more users of a security system inaccordance with a contact tree that defines the order in which the usersshould be reached. Based on the locations of the users' mobile devicesat or around the time that an alarm is triggered, such a call tree canbe dynamically determined and/or modified, before any of the users arecontacted, to increase the efficiency and likelihood of reaching thehighest priority user(s). For instance, if mobile device locationindicates that the first user in the call tree is not at home, then asecurity server can determine, based on the mobile device location forthe user, that alarm verification call(s) should be placed to the user'smobile phone instead of their home phone.

In other embodiments, instead of determining that a particular alarm isfalse, the alarm can be verified as legitimate. For example, if a firealarm is triggered at a premises and mobile device position informationindicates that a person was in the house just prior to the alarm beingtriggered and quickly exited to a nearby location outside of the houseafter the alarm was triggered, an evaluation of the circumstances mayresult in a determination that the fire alarm is legitimate and firstresponders are needed to extinguish a fire at the premises. As discussedbelow, these circumstances and others may be defined in look-up tablesand templates that can be used by various devices in evaluating alarms.

In some embodiments, other benefits may be provided by using mobiledevice location in determining how to respond to an alarm. For example,in situations where an alarm at a premises is real (rather than false)and emergency responders are dispatched to the premises, informationabout where certain mobile devices are located can be used to informfirst responders about how many people may require assistance at thepremises and what kinds of special needs they might have. For instance,mobile device location information may indicate that children or elderlypersons with special medical needs are at the premises, which canaccordingly be communicated to emergency responders to enable them tobetter respond to the alarm.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the disclosure are illustrated by way of example with respectto the accompanying figures, in which like reference numerals indicatesimilar elements, and in which:

FIG. 1 illustrates an example system in which various features discussedherein may be implemented;

FIG. 2 illustrates an example computing device that may be used toimplement any of the computing devices and servers discussed herein;

FIG. 3 illustrates an example premises at which a home security consolemay be deployed;

FIG. 4 illustrates an example of processing alarm signals according toone or more aspects of the disclosure;

FIG. 5 illustrates another example of processing alarm signals accordingto one or more aspects of the disclosure;

FIG. 6 illustrates a flowchart that depicts an example method ofprocessing alarm signals according to one or more aspects of thedisclosure; and

FIG. 7 illustrates a flowchart that depicts an example method ofresponding to a location request according to one or more illustrativeaspects of the disclosure.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

As introduced above, various aspects of the disclosure relate toprocessing alarm signals, particularly in situations where mobile devicelocation information can be used to determine whether an alarm islegitimate or false. In several of the examples that are discussedbelow, the ways in which alarm-related information can be obtained andanalyzed will be illustrated. Before turning to these examples, however,an example of an information distribution network which includes one ormore of the computing devices discussed below, and which can be used insending and receiving various messages and/or other data, will first bedescribed. In addition, an example of a computing device and varioushardware components that can be used in implementing one or more of thecomputing devices discussed herein will also be described.

FIG. 1 illustrates an example information distribution network 100 onwhich many of the various features described herein may be implemented.Network 100 may be any type of information distribution network, such asa satellite network, a telephone network, a cellular network, a wirelessnetwork, and/or combinations thereof. For example, network 100 may be anoptical fiber network, a coaxial cable network, or a hybrid fiber/coax(HFC) distribution network. Such a network 100 can use a series ofinterconnected communication links 101 (e.g., coaxial cables, opticalfibers, wireless connections, etc.) to connect multiple premises 102(e.g., businesses, homes, consumer dwellings, etc.) to a local office103 (e.g., a headend, a central office, a processing facility, etc.).The local office 103 may transmit downstream information signals ontothe links 101, and each premises 102 may have a receiver that can beused to receive and process those signals. The geographic location ofthe local office 103 can vary, and the local office 103 may be proximateto a user's neighborhood in some embodiments, while in otherembodiments, the local office 103 may be located remotely at acentralized location. The various servers can be located anywhere, andtheir location might not be relevant to a user (e.g., the servers may bein the “cloud”).

In some arrangements, there may be one link 101 originating from thelocal office 103, and it may be split a number of times to distributethe signal to various premises 102 in the vicinity (which may be manymiles) of the local office 103. The links 101 may include componentsthat are not illustrated, such as splitters, filters, amplifiers, etc.,to help convey the signal clearly. Some portions of the links 101 alsomay be implemented with fiber-optic cable, while other portions may beimplemented with coaxial cable, other lines, or wireless communicationpaths.

The local office 103 may include an interface 104, such as a terminationsystem (TS) or a cable modem termination system (CMTS) in an example ofan HFC-type network, which may be a computing device that is configuredto manage communications between devices on the network of links 101 andbackend devices, such as servers 105, 106, and 107 (which are discussedfurther below). In the example of an HFC-type network, the TS may be asspecified in a standard, such as the Data Over Cable Service InterfaceSpecification (DOCSIS), published by Cable Television Laboratories, Inc.(a.k.a. CableLabs), or it may be a similar or modified device instead.The TS may be configured to place data on one or more downstreamfrequencies to be received by modems at the various premises 102, and toreceive upstream communications from those modems on one or moreupstream frequencies. The local office 103 may also include one or morenetwork interfaces 108, which can permit the local office 103 tocommunicate with various other external networks 109. These networks 109may include, for example, Internet Protocol (IP) networks, Internetdevices, telephone networks, cellular telephone networks, fiber opticnetworks, local wireless networks (e.g., LTE, WiMAX, etc.), satellitenetworks, and any other desired network, and the interface 108 mayinclude the corresponding circuitry needed to communicate on the network109, and to communicate with other devices on the network, such as acellular telephone network and its corresponding cell phones (e.g.,cellular phone 117). Collectively, these networks 109 may be referred toherein as “the cloud” or “cloud architecture.”

As noted above, the local office 103 may include a variety of serversthat may be configured to perform various functions. For example, thelocal office 103 may include a back office server 105. The back officeserver 105 may generate push notifications related to functions, such asbilling, reporting, and subscriber management to deliver data and/orcommands to the various premises 102 in the network (or morespecifically, to the devices in the premises 102 that are configured todetect such notifications). The local office 103 may also include acontent server 106. The content server 106 may be one or more computingdevices that are configured to provide content to users, who may be, forexample, in the premises 102 (e.g., homes). In some embodiments, thecontent server 106 may include software to validate (or initiate thevalidation of) user identities and entitlements, locate and retrieve (orinitiate the location and retrieval of) requested content, encrypt thecontent, and initiate delivery (e.g., streaming, transmitting via aseries of content fragments) of the content to the requesting userand/or device. Other server computing devices may be present as well,such as one or more application servers 107, which are discussed below.Also, the various servers and elements are depicted in a local office103, but they need not be co-located in a common premises, and insteadmay have some or all elements located remotely in the network 109.

The local office 103 may further include one or more application servers107 and/or may communicate with one or more application servers 107 thatmay be maintained in the cloud 109. An application server 107 may be acomputing device configured to offer any desired service, and may runvarious languages and operating systems (e.g., servlets and JSP pagesrunning on Tomcat/MySQL, OSX, BSD, Ubuntu, Redhat, HTMLS, JavaScript,AJAX, and COMET). For example, an application server 107 may beresponsible for collecting television program listings information andgenerating a data download for electronic program guide listings.Another application server 107 may be responsible for monitoring userviewing habits and collecting that information for use in selectingadvertisements. Another application server may be responsible forformatting and inserting advertisements in a video stream and/or contentitem being transmitted to the premises 102. As discussed below, stillanother application server 107 may be used to monitor and/or otherwisecommunicate with one or more security systems that may be deployed atvarious locations, such as the premises 102.

An example premises 102 a may include an interface 120, which mayinclude a modem 110 (or another receiver and/or transmitter devicesuitable for a particular network), which may include transmitters andreceivers used to communicate on the links 101 and with the local office103. The modem 110 may be, for example, a coaxial cable modem (forcoaxial cable lines 101), a fiber interface node (for fiber optic links101), or any other desired modem device. The modem 110 may be connectedto, or be a part of, a gateway interface device 111. The gatewayinterface device 111 may be a computing device that communicates withthe modem 110 to allow one or more other devices in the premises 102 ato communicate with the local office 103 and other devices beyond thelocal office. The gateway 111 may be a set-top box (STB), digital videorecorder (DVR), computer server, or any other desired computing device.The gateway 111 may also include local network interfaces (not shown)that can provide communication signals to other devices in the premises102 a (e.g., user devices), such as televisions 112, additional STBs113, personal computers 114, laptop computers 115, wireless devices 116(e.g., wireless laptops and networks, mobile phones, mobile televisions,tablet computers, PDAs, etc.), and any other desired devices. Examplesof the local network interfaces may include Multimedia Over CoaxAlliance (MoCA) interfaces, Ethernet interfaces, universal serial bus(USB) interfaces, wireless interfaces (e.g., IEEE 802.11), 4G, WiMAX,LTE, Bluetooth interfaces, and others. In some embodiments, the systemmay use ZigBee and Z-Wave compliant devices.

FIG. 2 illustrates general hardware elements that can be used toimplement any of the various computing devices discussed herein. Thecomputing device 200 may include one or more processors 201, which mayexecute instructions of a computer program to perform any of thefeatures discussed herein. The instructions may be stored in any type ofcomputer-readable medium or memory, to configure the operation of theprocessor 201. For example, instructions may be stored in a read-onlymemory (ROM) 202, random access memory (RAM) 203, removable media 204,such as a Universal Serial Bus (USB) drive, compact disk (CD) or digitalversatile disk (DVD), floppy disk drive, or any other desired electronicstorage medium. Instructions may also be stored in an attached (orinternal) storage 205 (e.g., hard drive, flash, etc.). The computingdevice 200 may include one or more output devices, such as a display 206(or an external television), and may include one or more output devicecontrollers 207, such as a video processor. There may also be one ormore user input devices 208, such as a remote control, keyboard, mouse,touch screen, microphone, camera, etc. The computing device 200 may alsoinclude one or more network interfaces 209, such as input/outputcircuits (such as a network card) to communicate with an externalnetwork 210. The network interface 209 may be a wired interface,wireless interface, or a combination of the two. In some embodiments,the interface 209 may include a modem (e.g., a cable modem), and network210 may include the communication lines 101 discussed above, theexternal network 109, an in-home network, a provider's wireless,coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., aDOCSIS network), or any other desired network.

FIG. 2 shows an example hardware configuration. Modifications may bemade to add, remove, combine, and/or divide, etc., components asdesired. Additionally, the components illustrated may be implementedusing basic computing devices and components, and the same components(e.g., processor 201, ROM 202, user input devices 208, etc.) may be usedto implement any of the other computing devices and components describedherein. For example, the various components herein may be implementedusing computing devices having components such as a processor executingcomputer-executable instructions stored on a computer-readable medium(e.g., storage 205), as illustrated in FIG. 2 .

One or more aspects of the disclosure may be embodied in computer-usabledata and/or computer-executable instructions, such as in one or moreprogram modules, executed by one or more computers or other devices toperform any of the functions described herein. Generally, programmodules include routines, programs, objects, components, datastructures, etc. that perform particular tasks or implement particularabstract data types when executed by a processor in a computer or otherdata processing device. The computer executable instructions may bestored on one or more computer readable media, such as a hard disk,optical disk, removable storage media, solid state memory, RAM, etc. Thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents, suchas integrated circuits, field programmable gate arrays (FPGAs), and thelike. Particular data structures may be used to more effectivelyimplement one or more aspects of the disclosure, and such datastructures are contemplated as being within the scope of computerexecutable instructions and computer-usable data described herein.

Having described an example of an information distribution network andan example of a computing device that may be used in implementingvarious aspects of the disclosure, several examples illustrating howalarm signals may be processed in some embodiments will now be describedin greater detail.

FIG. 3 illustrates an example premises 300, such as a home, thatincludes a security system, such as a home security system. As seen inFIG. 3 , the home security system deployed at premises 300 may include ahome security console 305 and a number of sensors that can be configuredto detect various occurrences and/or other changes in state(s) atpremises 300. For example, the home security system deployed at premises300 may include a door sensor 310 that is configured to detect whether adoor at premises 300 is open or closed. In addition, the security systemdeployed at premises 300 may include a number of window sensors, such aswindow sensor 315 and window sensor 320, that are each configured todetect whether a particular window is open or closed. The home securitysystem deployed at premises 300 also may include a smoke detector 325that is configured to detect whether smoke is present at premises 300,and further may include a glass break sensor 330 that is configured todetect the sound associated with a window or other glass object breakingat the premises. Any and/or all of these sensors may be communicativelycoupled via one or more wired and/or wireless connections to homesecurity console 305, which may send and/or receive signals to and/orfrom the various sensors. In addition, by analyzing signals receivedfrom the various sensors, home security console 305 may be able todetermine whether one or more alert criteria are met, and accordingly,whether an alarm should be triggered and/or whether other alert actionsshould be taken. Additionally, while FIG. 3 shows a particular numberand configuration of sensors which may be included in a security systemdeployed at a premises in one embodiment, any number of sensors, as wellas any number of home security consoles and/or different types ofsensors, may be included in a home security system in other embodiments.

In addition to including a home security console and a number ofsensors, premises 300 also may include a gateway 335 and a display, suchas a television 340. In some embodiments, gateway 335 may implement oneor more aspects of the gateway interface device 111, which was discussedabove with respect to FIG. 1 . This may, for instance, include receivingand/or decoding content via an information distribution network, as wellas displaying and/or playing back such content on television 340. Insome additional and/or alternative embodiments, gateway 335 and homesecurity console 305 may be implemented in a single device that, forexample, is configured to both monitor the various sensors that areinstalled at premises 300 and facilitate electronic communications(e.g., with a local office, such as local office 103, via one or morecommunication networks, such as network 100, etc.).

During its typical course of operation, home security console 305 maymonitor signals received from the various sensors located at thepremises 300 and also may communicate with one or more other devicesthat are located at and/or used in the premises. Some of these otherdevices may be mobile devices (e.g., cellular phones, smart phones,tablet computers, etc.) that belong to various people who reside at thepremises. In exchanging various types of information with these mobiledevices, home security console 305 also may obtain location informationfrom the mobile devices that enables home security console 305 todetermine where particular mobile devices are at any given time, andsubsequently infer where certain users are located based on the locationof their respective device(s).

As discussed above, a security system, such as home security console305, may be able to determine, in some instances, that an alarm is false(and/or make other conclusions about the alarm) based on locationinformation received from one or more mobile devices. An example of sucha situation will now be discussed in greater detail with respect to FIG.4 .

FIG. 4 illustrates an example of processing alarm signals according toone or more aspects of the disclosure. In particular, the exampledepicted in FIG. 4 illustrates how certain techniques can be used toautomatically determine that an alarm is false and should bedeactivated.

As seen in FIG. 4 , an example premises 400 may include a securityconsole 405 and an entry door 410. A mobile device 415, which belongs toa resident of the premises 400, may be registered with the securityconsole 405. As a result of this registration, security console 405(and/or a security server that is integrated into or communicativelycoupled to security console 405) may be able to monitor the position ofmobile device 415 and make decisions about how to respond to an alarm atthe premises 400 based on the position of mobile device 415.

For instance, in the example situation illustrated in FIG. 4 , a usermay initiate an arming sequence by operating security console 405 (e.g.,to place the security system installed at premises 400 in an armedstate). The initiation of the arming sequence may start a countdowntimer that provides the user with a predetermined amount of time (e.g.,twenty seconds) to exit the premises 400 (e.g., via entry door 410)before the security system enters the armed state.

For whatever reason, however, the user in this example might not exitthe premises 400 quickly enough. As a result, the countdown timer mayexpire before the user exits the premises 400, and an alarm may betriggered. Despite the alarm being triggered, however, the user in thisexample might, for whatever reason, leave the premises 400 withoutmanually deactivating the alarm. For instance, the user might notrealize that the alarm has been triggered, or the user might be in ahurry and does not wish to take the time to deactivate the alarm.

With a conventional security system, the alarm in this example maycontinue to sound and other alarm actions, including actions thatescalate the alarm, may occur. For example, as the alarm continues atthe premises 400, police officers and/or other emergency responders maybe alerted and subsequently may travel to the premises 400 to respond tothe alarm. Because the alarm is a false alarm in the example, the usersubsequently may incur a fine or other penalty as a result of theemergency responders responding to the false alarm at the premises 400.

Using one or more aspects of the disclosure, however, some of thenegative consequences that might otherwise arise in this situation maybe mitigated, if not avoided entirely. For example, in accordance withone or more embodiments, security console 405 may obtain positioninformation from mobile device 415 and use the position information todetermine whether it is likely that the alarm triggered at premises 400is false. In particular, in the example illustrated in FIG. 4 , securityconsole 405 may be able to determine, upon analyzing positioninformation obtained from mobile device 415, that the user was insidepremises 400 just before the alarm was triggered and left the premises400 within a predetermined amount of time of the alarm being triggered(e.g., within ten seconds of the alarm being tripped). Based on thisdetermination, and potentially further based on one or more templatesthat define how such location information can be interpreted, thesecurity console 405 may determine that the circumstances surroundingthe alarm, as well as the position(s) of the mobile device 415 inrelation to the alarm being tripped, correlate with a profile defined inthe template(s) that are indicative of the alarm being false. Thesecurity console 405 may deactivate the alarm accordingly, which maypotentially avoid emergency responders being dispatched to the premises400, along with the other negative consequences of the false alarm.

In another example, a user of mobile device 415 may have armed thesecurity system installed at premises 400, and after forgetting that thesecurity system is armed, may have temporarily exited the premises 400(e.g., to take out the trash, to pick up the mail, to walk the dog,etc.). In this example, the security system may begin a countdownsequence while the user of mobile device 415 is in the driveway of thepremises 400, and the countdown sequence may end (with the alarmbeginning to sound) before the user of mobile device 415 can get backinside the house to disarm the security system. By implementing certainaspects of the disclosure, the alarm triggered by the security systemmay be automatically deactivated in these circumstances. For example, inaccordance with various embodiments, security console 405 may determine,based on position information obtained from mobile device 415, that theuser of mobile device 415 is located proximate to the premises 400 (orwithin a predetermined threshold distance of the premises 400, e.g.,because he or she is in the driveway or in the yard). Based on thisdetermination, and potentially further based on one or more templatesthat define how such location information can be interpreted (e.g., oneor more templates that define the predetermined threshold distance forthe user to be considered sufficiently close to the premises for thealarm to be deactivated), the security console 405 may determine thatthe circumstances surrounding the alarm, as well as the position(s) ofthe mobile device 415 in relation to the alarm being tripped, correlatewith a profile defined in the template(s) that are indicative of thealarm being false. The security console 405 may deactivate the alarm inaccordance with this determination, which may potentially avoidemergency responders being dispatched to the premises 400, along withthe other negative consequences of the false alarm.

In some instances, a security system may use mobile device positioninformation to provide other features, instead of or in addition toautomatically deactivating alarms that are likely false. For example,mobile device position information may be used, in some instances, toprovide enhanced information to emergency responders in situations wherean alarm is legitimate. As illustrated below, this enhanced informationmay include information about the residents and/or other occupants of aparticular premises, such as the number of people present in thepremises, the ages and/or special needs (e.g., medical conditions) ofthe residents and/or other occupants, and/or other information. Anexample of such a situation will now be discussed with respect to FIG. 5.

FIG. 5 illustrates another example of processing alarm signals accordingto one or more aspects of the disclosure. In particular, the exampledepicted in FIG. 5 illustrates how some aspects of the disclosure can beimplemented to enhance the ways in which a legitimate alarm is handled.

As seen in FIG. 5 , an example premises 500 may include a securityconsole 505, which may implement one or more aspects of the othersecurity consoles discussed above. Several mobile devices, includingmobile device 510, mobile device 515, mobile device 520, and mobiledevice 525 may be registered with security console 505, and securityconsole 505 may thus be able to monitor the locations of these variousmobile devices. Additionally, in this example, each of the four mobiledevices may be used by, and linked to, a different resident of thepremises 500. In particular, mobile device 510 may be linked to a firstchild who resides at premises 500, mobile device 515 may be linked to asecond child who resides at premises 500, mobile device 520 may belinked to a father who resides at premises 500, and mobile device 525may be linked to a mother who resides at premises 500.

In the example situation illustrated in FIG. 5 , the two children whoare registered users of mobile devices 510 and 515 may be home alone atthe premises 500, and the two parents who are registered users of mobiledevices 520 and 525 may be away from the home and at a remote location530 (e.g., at a restaurant, at a movie theater, etc.).

While the two parents are away from premises 500 and visiting the remotelocation 530, a fire alarm may, for example, be triggered at thepremises 500. After the fire alarm has been triggered, the securityconsole 505 may electronically report the file alarm to a local PublicSafety Answering Point (PSAP), which may coordinate a response to thefire alarm by one or more emergency responders (e.g., police units, firedepartment units, ambulances, etc.).

In addition to simply reporting the fire alarm to the local PSAP,however, security console 505 also may, in accordance with one or moreembodiments, collect and/or determine additional information about thepeople who may be present at the premises 500, and subsequently mayprovide this additional information to the local PSAP. For example,after the fire alarm is triggered, security console 505 may determinewhere all of the registered devices are located, as this may beindicative of where the users of these devices are located. In thisexample, this determination may further result in security console 505determining that the devices linked to the children who reside at thepremises (e.g., mobile devices 510 and 515) are located at the premises500, while the devices linked to the adults who reside at the premises(e.g., mobile devices 520 and 525) are located away from the premises500 at a remote location 530. Based on this location information,security console 505 subsequently may determine that the children arehome alone and that the adults are out of the house.

After the registered mobile devices have been located, security console505 may report any and/or all of the location information, as well asany and/or all of the determination results discussed above, to thelocal PSAP. The local PSAP may then, for instance, provide any and/orall of this information to first responders, who can better tailor theirresponse to the fire alarm with the benefit of having more informationabout the current circumstances at premises 500 beyond the mere factthat the fire alarm has been triggered there. For example, with theinformation provided by security console 505, the first responders maybe able to enter the premises 500 knowing that they need to locateand/or rescue at least two children. Other information may similarly beobtained and provided to fire responders in other instances, such as anyhealth conditions or other special needs of people who may be at thepremises 500. As discussed below, some of this information may beobtained from user profile data that can be stored by the home securityconsole 505.

Having described several example situations in which some aspects of thedisclosure may be utilized, an example of the processing that may beperformed (e.g., by a security console) in some embodiments will now bediscussed in greater detail with respect to FIG. 6 .

FIG. 6 illustrates a flowchart that depicts an example method ofprocessing alarm signals according to one or more aspects of thedisclosure. In some embodiments, the method illustrated in FIG. 6 can beperformed by a security console located at a particular premises (e.g.,home security console 305 at premises 300), or by a security server thatis communicatively coupled to the security console and located remotelyfrom the premises (e.g., at local office 103). In other embodiments, oneor more steps of the method may additionally or alternatively beperformed by another device (e.g., by another security console that isalso located at the same premises, in a situation where two or moresecurity consoles are present at the premises). While a number of stepsare illustrated in the figures (including the steps illustrated in FIG.6 ) and discussed below as being performed in a certain order in someembodiments, in other embodiments, these steps may be performed indifferent orders. In addition, some steps may be combined or might notbe performed at all, and/or one or more additional or alternative stepsmay be performed in addition to or instead of those illustrated in thefigures and discussed below.

When initially powered on, the particular computing device that isperforming the method illustrated in FIG. 6 may first execute a numberof configuration steps. For example, in step 601, the device (e.g., asecurity console, such as security console 305; a security server, suchas application server 107; etc.) may load a number of differentvariables and settings. Examples of the types of variables and settingsthat may be loaded include user preferences (e.g., regarding passcodesfor the security system, a length of time to be used for the countdowntimer during the arming process, etc.), networking information (e.g.,network addresses for sensors installed at the premises, networkaddresses for one or more monitoring server(s) that monitor the securitysystem at the premises, etc.), and user profile information (e.g.,identifiers associated with previously registered user devices, variousinformation about different people who reside at the premises, includingtheir names, ages, health conditions, special needs, etc.).

In step 602, the computing device (e.g., the security console, thesecurity server, etc.) may initialize one or more communication links.This initialization may, for instance, include establishing electronicconnections (e.g., via one or more networks, such as distributionnetwork 100) with one or more sensors installed at the premises, one ormore monitoring servers, and other servers and devices with which thecomputing device may exchange data (e.g., a server operated by a local PSAP).

In step 603, the computing device (e.g., the security console, thesecurity server, etc.) may register one or more mobile devices. Thisregistration may, for instance, enable the security console to recognizethe registered device(s) as belonging to a particular person who residesat the premises where the security system is installed, and in someembodiments, this registration may be initiated and/or completed on oneof the mobile devices being registered (e.g., by a user of such a mobiledevice). In some instances, the one or more mobile devices registered instep 603 may be mobile devices that have not been previously registeredwith the security console, while in other instances, the securityconsole may re-register previously registered mobile devices each timethat the security console is powered on and/or initialized.

In registering with one or more mobile devices, the computing device(e.g., the security console, the security server, etc.) may request,receive, and store identification information that can be used toidentify the mobile devices themselves, as well as user profileinformation that can be used to provide more customized experiences tothe users of these mobile devices. For example, the user profileinformation that may be requested, received, and stored by the securityconsole (or other computing device) may include the name(s), age(s),gender(s), language preference(s), health condition(s), special need(s),family relationship(s) (e.g., the identities of the user's mother,father, sibling(s), spouse, etc.), and/or other information for eachperson who may use each of the mobile devices being registered. In someinstances, a particular mobile device may be used by more than oneresident of the premises (e.g., two children may share a single tabletcomputer). In these instances, user profile information may berequested, received, and stored for each user of the mobile deviceduring registration, as this information may later be used by thesecurity console in processing alarm signals (e.g., if user profileinformation indicates that a certain mobile device has multiple users,then when and/or after an alarm has been tripped, the security consolemay prompt the user(s) to identify which user(s) are with the device, soas to enable one or more aspects of the location-based alarm processingdiscussed herein).

After performing one or more of these configuration steps, the computingdevice (e.g., the security console, the security server, etc.) may entera monitoring loop in which it periodically checks the state of varioussensors at the premises (e.g., in step 604) and subsequently determines,based on the states of the sensors, whether alert criteria have been metand whether an alarm has accordingly been tripped (e.g., in step 605).In addition to checking the states of various sensors, the securityconsole also may perform other actions during this monitoring loop. Forexample, the security console also may send and/or receive heartbeatmessages to and/or from other devices that are located at the premisesor at another location, the security console may update or otherwisemaintain one or more counters and/or clocks, and the security consolemay perform other idle processing actions.

If it is determined during the monitoring loop that an alarm has beentripped (e.g., in step 605), then the computing device (e.g., thesecurity console, the security server, etc.) may perform a series ofsteps in order to locate the registered mobile devices and determine howto respond to the alarm.

For example, in step 606, the computing device (e.g., the securityconsole, the security server, etc.) may determine what type of alarm hasbeen triggered. Different types of alarms may, for instance, includeburglar alarms, fire alarms, medical alarms, and other types of alarms.The device's response to a particular alarm may depend on the type ofalarm that has been triggered, as different types of alarms may call fordifferent types of responses.

In step 607, the computing device (e.g., the security console, thesecurity server, etc.) may load a response file. The particular responsefile that is loaded may be selected based on the type of alarm that hasbeen triggered. The response file may, for example, include a look-uptable that defines a template for responding to alarms of a certain typebased on the circumstances surrounding the alarm that has beentriggered. For instance, a look-up table that defines a template forresponding to burglar alarms may specify various sets of circumstancesthat are indicative of, and can be used in identifying, false alarms insituations where a burglar alarm has been tripped. These sets ofcircumstances may be defined in terms of different sensor conditions(e.g., which sensors tripped, in which order were the sensors tripped,etc.), different timing considerations (e.g., how much time elapsedsince the mobile device(s), and presumably the user(s), were located ata particular location, such as in the premises or by a particular entrydoor of the premises, etc.), different mobile device movement patterns(e.g., whether the mobile device(s) are moving towards or away from thepremises, as well as the direction and/or speed at which such device(s)are traveling, etc.), and/or other conditions that can be sensed orotherwise determined by the mobile device or the security console. Anexample of such a look-up table, which includes different sets ofcircumstances for evaluating a burglar alarm, is illustrated in TABLE Abelow:

TABLE A Time Con- Since Mobile dition Time Mobile Device Set Sensor(s)Since Device Proximity Alarm Num- Sensor(s) Not Alarm Was at to Likelyber Tripped Tripped Started Premises Premises False? 1 Front Back 30 25Within Yes Door Door seconds seconds 200 Sensor Sensor; yards FirstFloor Motion Sensors; Second Floor Motion Sensors 2 Back Front 30 20Within Yes Door Door seconds seconds 400 Sensor; Sensor; yards FirstSecond Floor Floor Motion Motion Sensors Sensors 3 First Floor Front 152 More No Motion Door seconds hours than Sensors; Sensor; 10 miles FirstBack Floor Door Glass Sensor; Break Second Sensor Floor Motion Sensors

While the examples discussed above involve loading a response file, thecomputing device may, in other embodiments, load a look-up table (that,e.g., defines a template for responding to alarms) from another source.For example, in some arrangements, such a look-up table may be storedand/or maintained in a central database (e.g., rather than as a localresponse file). In these arrangements, the computing device may, in step607, load the look-up table by accessing and/or retrieving informationfrom such a central database (e.g., rather than loading a local responsefile to retrieve the table).

After loading an appropriate response file (e.g., in step 607), in step608, the computing device (e.g., the security console, the securityserver, etc.) may poll the one or more registered mobile devices inorder to obtain information about where the registered devices arecurrently located. This polling may, for instance, include sending arequest for current or updated location information to the mobiledevice(s), and further may include receiving location information fromthe mobile device(s) in response to such a request. In some instances,the location information received from a particular mobile device maysimply include the geographic coordinates of a single point thatrepresents the mobile device's current position. In other instances,such location information may additionally or alternatively include aset of geographic coordinates, as well as corresponding timestampinformation, that together model a recent trajectory or motion patternof the mobile device.

In step 609, the computing device (e.g., the security console, thesecurity server, etc.) may evaluate the location information receivedfrom the one or more registered mobile devices in order to determine howto respond to the alarm. In evaluating this location information, thecomputing device may compare the location information and the state ofvarious sensors at the premises with the look-up table included in theresponse file. Based on this comparison, the computing device maydetermine which set of circumstances in the look-up table most closelymatches the actual circumstances (e.g., in terms of how the alarm wastripped and where the registered device(s) are), and subsequently maydetermine how to respond to the alarm based on this matching. Forexample, if the computing device determines, based on the actualcircumstances and an appropriate look-up table, that the alarm is likelyfalse, then the computing device may determine to automaticallydeactivate the alarm.

In step 610, the computing device (e.g., the security console, thesecurity server, etc.) may perform the one or more actions (e.g.,determined in step 609) in order to respond to the alarm. For example,if it was determined in step 609 that the alarm should be deactivated,then in step 610, the security console may deactivate the alarm.Thereafter, the computing device may return to the monitoring loopdiscussed above (e.g., to periodically check sensor status in step 604and determine whether an alarm has been tripped in step 605), or themethod may end.

As illustrated above, the ways in which a computing device, such as asecurity console, responds to a particular alarm may depend on thelocation information received from the registered mobile device(s) andon the template defined in the look-up table. In some instances, inaddition to (or instead of) determining that an alarm is false andshould be deactivated, the computing device may also (or instead)determine and perform other actions in responding to an alarm at apremises.

For example, a security console may, in some instances, determine thatan abort window should be modified based on the location(s) ofregistered mobile device(s). Such an abort window may, for instance,specify an amount of time that the security console will wait beforealerting first responders (e.g., by sending a request for help to alocal PSAP) once an alarm is triggered at a premises. Thus, in oneexample, if the security console determines that a burglar alarm hasbeen tripped and a registered mobile device is present at the premises,the security console may modify an abort window to extend the amount oftime that a user has to manually deactivate the alarm before policeunits are called. In some arrangements, an alarm at the premises may beverified before first responders are notified (e.g., before a local PSAPis contacted about the alarm). In some instances, an alarm may beverified at a central station (which may, e.g., be included in localoffice 103 and/or in another location and/or office) by a securityprofessional based on data obtained from and/or presented by thesecurity system at the premises. In other instances, an alarm may beverified at the premises (e.g., by a resident of the premises) based onsimilar information. In verifying the alarm, the security professionaland/or the resident may, for instance, evaluate and decide whether anemergency is occurring at the premises and whether the local PSAP shouldbe contacted accordingly.

In other instances, a security console may dynamically determine and/ormodify a call tree based on the location(s) of registered mobiledevice(s). Such a call tree may, for instance, specify two or morecontact telephone numbers that can be dialed in a certain order inattempting to reach one or more resident(s) of the premises when analarm needs to be verified. If, for example, the security consoledetermines, based on mobile device location information that aparticular resident of the premises is not at home, then the securityconsole may determine and/or modify a call tree to prioritize theresident's mobile telephone number over his or her home telephonenumber. Although dialing telephone numbers are discussed in severalexamples here, in some instances, a call tree may additionally oralternatively include other forms of contact information (e.g., inaddition to or instead of telephone numbers), which may enable thesecurity console to contact resident(s) via other modes ofcommunication. For example, the call tree may include one or more mobilephone numbers (e.g., which may enable the security console to contactresident(s) using text messaging, such as SMS and/or MMS, pushnotification, email, etc.), one or more email addresses (e.g., which mayenable the security console to contact resident(s) via email), and/orone or more screen names (e.g., which may enable the security console tocontact resident(s) via instant messaging). Any other forms ofcommunication may likewise be included in a call tree, as may bedesired.

In still other instances, in responding to an alarm at a premises, asecurity console may determine presence information based on thelocation(s) of registered mobile device(s). Such presence informationmay, for example, include the number of registered mobile device(s)present at the premises, an estimated number of people present at thepremises (e.g., determined based on the number of mobile device(s) thatare present at the premises), and/or personal information about thepeople who are likely at the premises (e.g., based on their mobiledevice(s) being present at the premises). In addition, this personalinformation may include the names and ages of the people who are likelyat the premises, as well as other information about these people,including their language abilities and preferences, any known medicalconditions, disabilities, special needs, etc. As noted above, any and/orall of this personal information may be stored and maintained by theregistered mobile devices and/or the security console as user profiledata.

In some instances, in evaluating location information from theregistered mobile device(s), the security console also may considerrecent locations and/or changes in position of the registered mobiledevice(s) in addition to the current position(s) of the device(s). Forexample, the security console may consider changes in position of theregistered mobile device(s) to determine that a user of one of thedevices is moving farther away from the premises. This determination canthen be used by the security console in determining how to respond tothe alarm (e.g., as a user's direction of travel relative to thepremises may be a factor that is evaluated in accordance with certainresponse files and/or look-up tables).

In other instances, in evaluating location information from theregistered mobile device(s), the security console also may verify analarm at the premises as being legitimate based on the locationinformation. For example, if a fire alarm has been tripped at thepremises and the security console (and/or one or more related systems,e.g., a security server or other security device) determines, inevaluating the location information from the registered mobiledevice(s), that the resident(s) are fleeing the premise(s), then thesecurity console may determine that the alarm is legitimate and thatfirst responders (e.g., the fire department) are needed at the premises.As a result of verifying the legitimacy of the fire alarm in this way,the security console may, for instance, expedite the process ofnotifying the local PSAP that assistance is needed at the premises(e.g., by shortening an abort window that might otherwise allow aresident of the premises to manually deactivate the fire alarm).

In addition to taking into account the locations of registered mobiledevices and other circumstances surrounding an alarm, such as the stateof various sensors, the security console also may consider other factorsin determining how to respond to an alarm at a premises. For instance,in some embodiments, the one or more mobile devices registered with thesecurity console (e.g., in step 603 of the example method discussedabove) may be prioritized. This prioritization can then be used by thesecurity console in evaluating location information obtained from themobile devices and in determining how to respond to an alarm.

For example, in some instances, a user might have multiple mobiledevices, such as a smart phone and a tablet computer, and both of thesedevices may be registered with the security console as belonging to thissame user. In these instances, the two mobile devices may be prioritizedby the security console in order to reflect the different ways in whichthe devices are used. For instance, the user may typically take theirsmart phone with them whenever they leave the house, but may typicallyleave the tablet computer at home and only occasionally take it out ofthe house. Thus, the user may provide input to the security console thatprioritizes the smart phone over the tablet computer when evaluatingmobile device location information in alarm response situations, as thesmart phone may be a better indicator of the user's location than thetablet computer.

In other instances, the security console may infer a user's position asbeing different from the position(s) of the user's registered mobiledevice(s). Such an inference may, in some circumstances, more accuratelyreflect the actuality of a situation where the user is not in the sameplace as his or her registered mobile device(s). For example, in asituation where the user is home alone and a fire alarm trips at thepremises, the security console may detect that after the fire alarm wastriggered, the front door was opened (e.g., based on a change in stateof a door sensor) and motion was detected in an entry hallway (e.g.,suggesting that the user has left the house). In this example situation,however, mobile device position information may indicate that the user'sregistered mobile device is still inside the house (e.g., because theuser left his or her smart phone behind when fleeing the house). Basedon these circumstances, the security console may infer that the user isin a different place than his or her mobile device and may determinethat the user has instead left the premises. The security console maysubsequently use this inference in reporting the number of peopleexpected to be inside the house to first responders, for instance, whennotifying a local PSAP of the fire alarm (e.g., by generating anautomated telephone call to the local PSAP and using text-to-speechfunctionality to inform an operator at the local PSAP of theseconditions; by generating and sending a text message to the local PSAPand/or a message receiving system at such a PSAP; etc.). The securityconsole may also report this information (e.g., “Device is in the home,but door was opened so user may have abandoned it.”) to the firstresponder, and allow the first responder to take that into account whenresponding to the alarm. The monitoring and reporting may continue evenafter the alarm has been triggered, and after the initial message hasbeen sent. For example, if the user fled the house, and then is able tolog into an account from their neighbor's house, the user can send amessage updating the alarm to indicate that the user has reached safety.This information can then be passed to the first responders, updatingthem. If the neighbor was on the user's list of contacts, then when thefire alarm was triggered, the security system may send a message to theneighbor's registered device (e.g., a computer, smartphone, etc.),displaying the message “Your neighbor Joe's fire alarm is tripped.”, andalso giving the option of an updated response (e.g., “If Joe is withyou, please ask him to enter his ID and password.”).

Having discussed several examples of the processing that may beperformed by a security console and/or a security server in implementingvarious aspects of the disclosure, some examples of the processing thatmay be performed by a mobile device in some embodiments will now bediscussed with respect to FIG. 7 .

FIG. 7 illustrates a flowchart that depicts an example method ofresponding to a location request according to one or more illustrativeaspects of the disclosure. As indicated above, the method illustrated inFIG. 7 can be performed by a mobile device (e.g., a smart phone, atablet computer, etc.) or any other kind of user device which can beused with the example security system discussed above. The mobile devicemay, for example, implement one or more aspects of the computing device200 illustrated in FIG. 2 . In some embodiments, one or more steps ofthe method illustrated in FIG. 7 may additionally or alternatively beperformed by a computing device that is communicatively coupled to sucha mobile device, such as an assistance server or cloud server whichassists the mobile device in performing certain processing functions. Asindicated above, while a number of steps are illustrated in the figures(including the steps illustrated in FIG. 7 ) and discussed below asbeing performed in a certain order in some embodiments, in otherembodiments, these steps may be performed in different orders. Inaddition, some steps may be combined or might not be performed at all,and/or one or more additional or alternative steps may be performed inaddition to or instead of those illustrated in the figures and discussedbelow.

When it is initially powered on, the particular mobile device that isperforming the method illustrated in FIG. 7 may first execute a numberof configuration steps. For example, in step 701, the mobile device mayinitialize one or more communication links. This initialization may, forinstance, include initializing one or more cellular interfaces and/orone or more wireless networking interfaces (e.g., IEEE 802.11a/b/g/ninterfaces, other WLAN interfaces, etc.), and also may includeestablishing connections to one or more cellular networks and/or WLANnetworks via such interfaces.

In step 702, the mobile device may initialize one or more locationservices that allow the mobile device to track its location and providelocation information to other devices, such as a security console. Thisinitialization may, for example, include initializing one or moresatellite positioning services (e.g., GPS services) and/or otherpositioning services (e.g., WLAN-based positioning). In some instances,the mobile device also may obtain an initial position fix once itinitializes its location services so as to enable subsequent locationtracking.

In step 703, the mobile device may register with a security console. Inregistering with the security console, the mobile device may prompt auser to select a detected security console for registration and/or mayexchange registration information with the security console, such as aunique identifier associated with the mobile device, a network addressassigned to the mobile device, and any other information as may bedesired. In some instances, if the mobile device has been previouslyregistered with a security console, then the mobile device might notre-register with the same security console in step 703. Rather, themobile device may simply send a notification message to the securityconsole to inform the security console that it is once again presentand/or online. Such a notification may, in some instances, includeupdated location information for the mobile device, such as the initialposition fix determined in step 702, which can then be used by thesecurity console to track the position of the mobile device.Additionally or alternatively, this location information can be providedby the mobile device to the security console in response to a message(e.g., a ping) received by the mobile device from the security console.

After performing one or more of these configuration steps, the mobiledevice may enter a standby loop in which it periodically sends aheartbeat message to the security console (e.g., in step 704) anddetermines whether an alarm message has been received from the securityconsole (e.g., in step 705). In some instances, the heartbeat messagemay include location information that describes the current location ofthe mobile device, which may, for example, enable the security consoleto track changes in position of the mobile device. Additionally oralternatively, the mobile device may send the heartbeat message to thesecurity console in response to a heartbeat message received by themobile device from the security console. For example, in some instances,the mobile device may send a message that includes such locationinformation in response to a polling request sent by the securityconsole. In these instances, the security console may be configured toperiodically poll the mobile device (and/or other registered mobiledevices) in order to obtain and track location information associatedwith the mobile device(s).

If it is determined during this standby loop that an alarm message hasbeen received from the security console, then the mobile device mayperform a series of steps to provide its current location to thesecurity console (e.g., so as to enable the processing at the securityconsole discussed above) and to provide the user of the mobile devicewith additional control over the alarm. In some instances, such an alarmmessage may be received as one or more text messages (e.g., an SMSmessage, an MMS message, etc.), instant messages, and/or pushnotifications. Additionally or alternatively, while such an alarmmessage that initially notifies the mobile device of an alarm at thepremises may be received as one of these types of messages, additionaldata (e.g., data received from the security console after the initialalarm message) may be received via a generic IP connection (which may,e.g., be established with the security console by the mobile device inresponse to receiving an initial alarm message).

For example, in step 706, the mobile device may determine its currentlocation. In determining its location, the mobile device may, forinstance, analyze satellite positioning signals (e.g., GPS signals)which it has received and/or other signals (e.g., cellular signals, WLANsignals, etc.) which it may have received. Based on these signals, themobile device may be able to calculate or otherwise determine itscurrent position (e.g., in geographic coordinates, such as latitude andlongitude).

In step 707, the mobile device may send location information to thesecurity console. This location information may represent the positionof the mobile device determined in step 706 and may, for example, beexpressed in terms of geographic coordinates. Additionally oralternatively, the location information may include a set ofcoordinates, with timing information, that models the mobile device'smovement over a predetermined amount of time (e.g., a period of time,such as 60 seconds, leading up to the alarm message being received).

In step 708, the mobile device may notify the user of the alarm. Innotifying the user of the alarm, the mobile device may, for example,play an audio alert and/or display a dialog box or prompt. In someinstances, such a prompt may be configured to allow the user to cancelthe alarm by clicking on a button or providing other input in responseto the prompt.

In step 709, the mobile device may display additional alarm content,such as images, audio, and/or live video from the premises (e.g.,captured by the security system at the premises). In some instances,this additional alarm content may be included in the prompt provided instep 708, while in other instances, the additional alarm content may bedisplayed by the mobile device in response to receiving a user requestfor more information about the alarm. By providing this additional alarmcontent to the user, the mobile device may be able to assist the user indeciding whether to manually cancel the alarm (e.g., using the promptprovided in step 708) and/or whether to manually contact the local PSAPto speak with first responders.

In step 710, the mobile device may send additional response data to thesecurity console (e.g., a security console, a security server, anothersecurity device, etc.). This additional response data may, for instance,include information indicating whether the user has requested tomanually deactivate the alarm (e.g., using the prompt provided in step708) and/or any other information as may be desired. Thereafter, themobile device may return to the standby loop discussed above (e.g., toperiodically send a heartbeat message in step 704 and to determinewhether an alarm message has been received in step 705). Alternatively,the method may end.

In addition to allowing a user to manually deactivate an alarm that hasbeen tripped and remotely control other aspects of a security system,the mobile device discussed above also may be configured to provideadditional and alternative functionalities in some additionalembodiments.

For example, in some instances, in response to providing an alarmnotification to a user in step 708, the mobile device may receive inputthat includes a user request to contact a local PSAP for the premises,and the mobile device may process this input and facilitate thiscontact. Notably, it is possible that when the mobile device is locatedaway from the premises, the mobile device may be in a region that isserved by a different PSAP than the PSAP that serves the premises. As aresult, a conventional 911 call by the user of the mobile device might,in these circumstances, not reach the right PSAP, and the user might notbe able to discuss the alarm with the first responders who areresponding to the alarm at the premises.

In accordance with some embodiments, however, the mobile device may beconfigured to identify an appropriate PSAP for the premises in responseto receiving the user request to contact a PSAP. This identificationmay, for example, be based on registration information obtained from thesecurity console (e.g., in step 703) that specifies the geographiclocation of the premises. In addition, after identifying the appropriatePSAP for the premises, the mobile device may initiate a call to theidentified PSAP, which may enable the user to speak with the correctfirst responders.

Many aspects of the disclosure have been described in terms ofillustrative embodiments. While illustrative systems and methods havebeen described which embody various aspects, the scope of the disclosureis not limited to these embodiments. Modifications may, for example, bemade, particularly in light of the explanation provided above. Forinstance, each of the features discussed in the examples above can beutilized alone or in combination or subcombination with elementsdiscussed in other examples. Any of the systems and methods (or partsthereof) may be combined with any other systems, methods, and partsdiscussed above. Any and/or all of the methods discussed herein can beembodied as computer-executable instructions stored on acomputer-readable medium, such as a non-transitory computer-readablememory.

Thus, modifications may be made without departing from the true spiritand scope of the present disclosure. The description should therefore beregarded as illustrative instead of restrictive.

The invention claimed is:
 1. A method comprising: receiving, by acomputing device associated with a security system, an indication of analarm triggering event at a premises; based on receiving the indicationof the alarm triggering event, determining at least one sensorcondition, wherein the at least one sensor condition is associated withat least one sensor of the premises; and determining, based on the atleast one sensor condition and information indicating a false alarm,that an alarm at the premises associated with the alarm triggering eventis a false alarm.
 2. The method of claim 1, further comprising: based onthe determining that the alarm at the premises is a false alarm,performing at least one of the following: deactivating the alarm;extending an abort window associated with the alarm; determining acontact method for sending a message indicating the false alarm;confirming a status of the at least one sensor; or causing adjustment ofa countdown timer associated with the alarm.
 3. The method of claim 1,wherein the at least one sensor is associated with a doorway.
 4. Themethod of claim 1, wherein the at least one sensor condition indicatesthat a first door sensor is in a tripped state and that a second doorsensor is in an untripped state.
 5. The method of claim 1, furthercomprising: causing, based on a period of time since a mobile device,associated with the premises, left the premises, adjusted output of thealarm.
 6. The method of claim 1, further comprising: causing, based onlocation information of a mobile device associated with the premises,adjusted output of the alarm.
 7. The method of claim 1, wherein the atleast one sensor comprises at least one of: a door sensor; a floormotion sensor; or a glass break sensor.
 8. The method of claim 1,further comprising: receiving current location information of a userdevice; and sending, to the user device and based on the currentlocation information of the user device, a message indicating that thealarm is a false alarm.
 9. A method comprising: receiving, by acomputing device associated with a security system, an indication of analarm triggering event at a premises; based on receiving the indicationof the alarm triggering event, determining at least one sensor conditionthat is associated with at least one sensor of the premises; and basedon determining that the at least one sensor condition is indicative of afalse alarm, determining that an alarm at the premises associated withthe alarm triggering event is a false alarm.
 10. The method of claim 9,further comprising: based on the determining that the alarm at thepremises is a false alarm, performing at least one of the following:deactivating the alarm; extending an abort window associated with thealarm; determining a contact method for sending a message indicating thefalse alarm; confirming a status of the at least one sensor; or causingadjustment of a countdown timer associated with the alarm.
 11. Themethod of claim 9, wherein the at least one sensor condition isindicative of a false alarm based on a first door sensor being in atripped state and a second door sensor being in an untripped state. 12.The method of claim 9, wherein the at least one sensor condition isindicative of a false alarm based on an order in which at least twosensors are tripped.
 13. The method of claim 9, further comprising:causing, based on a period of time since a mobile device, associatedwith the premises, left the premises, adjusted output of the alarm. 14.The method of claim 9, further comprising: causing, based on locationinformation of a mobile device associated with the premises, adjustedoutput of the alarm.
 15. The method of claim 9, further comprising:based on the determining that the alarm at the premises is a falsealarm, sending messages, indicating the false alarm, to a plurality oftelephone numbers in an order that is indicated by informationassociated with the security system.
 16. An apparatus comprising: one ormore processors; and memory comprising instructions that, when executedby the one or more processors, cause the apparatus to: receive anindication of an alarm triggering event at a premises; based onreceiving the indication of the alarm triggering event, determine atleast one sensor condition, wherein the at least one sensor condition isassociated with at least one sensor of the premises; and determine,based on the at least one sensor condition and information indicating afalse alarm, that an alarm at the premises associated with the alarmtriggering event is a false alarm.
 17. The apparatus of claim 16,wherein the instructions, when executed by the one or more processors,cause the apparatus to: based on the determining that the alarm at thepremises is a false alarm, perform at least one of the following:deactivate the alarm; extend an abort window associated with the alarm;determine a contact method for sending a message indicating the falsealarm; confirm a status of the at least one sensor; or cause adjustmentof a countdown timer associated with the alarm.
 18. The apparatus ofclaim 16, wherein the at least one sensor is associated with a doorway.19. The apparatus of claim 16, wherein the at least one sensor conditionindicates that a first door sensor is in a tripped state and that asecond door sensor is in an untripped state.
 20. The apparatus of claim16, wherein the instructions, when executed by the one or moreprocessors, cause the apparatus to cause, based on a period of timesince a mobile device, associated with the premises, left the premises,adjusted output of the alarm.
 21. The apparatus of claim 16, wherein theinstructions, when executed by the one or more processors, cause theapparatus to: cause, based on location information of a mobile deviceassociated with the premises, adjusted output of the alarm.
 22. Theapparatus of claim 16, wherein the at least one sensor comprise at leastone of: a door sensor; a floor motion sensor; or a glass break sensor.23. The apparatus of claim 16, wherein the instructions, when executedby the one or more processors, cause the apparatus to: receive currentlocation information of a user device; and send, to the user device andbased on the current location information of the user device, a messageindicating that the alarm is a false alarm.
 24. An apparatus comprising:one or more processors; and memory comprising instructions that, whenexecuted by the one or more processors, cause the apparatus to: receivean indication of an alarm triggering event at a premises; based onreceiving the indication of the alarm triggering event, determine atleast one sensor condition that is associated with at least one sensorof the premises; and based on a determination that the at least onesensor condition is indicative of a false alarm, determine that an alarmat the premises associated with the alarm triggering event is a falsealarm.
 25. The apparatus of claim 24, wherein the instructions, whenexecuted by the one or more processors, cause the apparatus to: based onthe determining that the alarm at the premises is a false alarm, performat least one of the following: deactivate the alarm; extend an abortwindow associated with the alarm; determine a contact method for sendinga message indicating the false alarm; confirm a status of the at leastone sensor; or cause adjustment of a countdown timer associated with thealarm.
 26. The apparatus of claim 24, wherein the at least one sensorcondition is indicative of a false alarm based on a first door sensorbeing in a tripped state and a second door sensor being in an untrippedstate.
 27. The apparatus of claim 24, wherein the at least one sensorcondition is indicative of a false alarm based on an order in which atleast two sensors are tripped.
 28. The apparatus of claim 24, whereinthe instructions, when executed by the one or more processors, cause theapparatus to: cause, based on a period of time since a mobile device,associated with the premises, left the premises, adjusted output of thealarm.
 29. The apparatus of claim 24, wherein the instructions, whenexecuted by the one or more processors, cause the apparatus to: cause,based on location information of a mobile device associated with thepremises, adjusted output of the alarm.
 30. The apparatus of claim 24,wherein the instructions, when executed by the one or more processors,cause the apparatus to: based on the determining that the alarm at thepremises is a false alarm, send messages, indicating the false alarm, toa plurality of telephone numbers in an order that is indicated byinformation associated with a security system at the premises.
 31. Themethod of claim 9, wherein the at least one sensor condition comprisesat least two sensor conditions.
 32. The apparatus of claim 24, whereinthe at least one sensor condition comprises at least two sensorconditions.
 33. A non-transitory computer-readable medium storinginstructions that, when executed, cause: receiving an indication of analarm triggering event at a premises; based on receiving the indicationof the alarm triggering event, determining at least one sensor conditionthat is associated with at least one sensor of the premises; and basedon determining that the at least one sensor condition is indicative of afalse alarm, determining that an alarm at the premises associated withthe alarm triggering event is a false alarm.
 34. The non-transitorycomputer-readable medium of claim 33, wherein the instructions, whenexecuted, cause: based on the determining that the alarm at the premisesis a false alarm, performing at least one of the following: deactivatingthe alarm; extending an abort window associated with the alarm;determining a contact method for sending a message indicating the falsealarm; confirming a status of the at least one sensor; or causingadjustment of a countdown timer associated with the alarm.
 35. Thenon-transitory computer-readable medium of claim 33, wherein the atleast one sensor condition is indicative of a false alarm based on afirst door sensor being in a tripped state and a second door sensorbeing in an untripped state.
 36. The non-transitory computer-readablemedium of claim 33, wherein the at least one sensor condition isindicative of a false alarm based on an order in which at least twosensors are tripped.
 37. The non-transitory computer-readable medium ofclaim 33, wherein the instructions, when executed, cause: causing, basedon a period of time since a mobile device, associated with the premises,left the premises, adjusted output of the alarm.
 38. The non-transitorycomputer-readable medium of claim 33, wherein the instructions, whenexecuted, cause: causing, based on location information of a mobiledevice associated with the premises, adjusted output of the alarm. 39.The non-transitory computer-readable medium of claim 33, wherein theinstructions, when executed, cause, based on the determining that thealarm at the premises is a false alarm, sending messages, indicating thefalse alarm, to a plurality of telephone numbers in an order that isindicated by information associated with a security system.
 40. Thenon-transitory computer-readable medium of claim 33, wherein the atleast one sensor condition comprises at least two sensor conditions. 41.A system comprising: a first computing device comprising: one or morefirst processors; and first memory storing first instructions that, whenexecuted by the one or more first processors, cause the first computingdevice to: receive an indication of an alarm triggering event at apremises; based on receiving the indication of the alarm triggeringevent, determine at least one sensor condition that is associated withat least one sensor of the premises; and based on a determination thatthe at least one sensor condition is indicative of a false alarm,determine that an alarm at the premises associated with the alarmtriggering event is a false alarm; and a second computing devicecomprising: one or more second processors; and second memory storingsecond instructions that, when executed by the one or more secondprocessors, cause the second computing device to: send the indication ofthe alarm triggering event at the premises.
 42. The system of claim 41,wherein the first instructions, when executed by the one or more firstprocessors, cause the first computing device to: based on thedetermining that the alarm at the premises is a false alarm, perform atleast one of the following: deactivate the alarm; extend an abort windowassociated with the alarm; determine a contact method for sending amessage indicating the false alarm; confirm a status of the at least onesensor; or cause adjustment of a countdown timer associated with thealarm.
 43. The system of claim 41, wherein the at least one sensorcondition is indicative of a false alarm based on a first door sensorbeing in a tripped state and a second door sensor being in an untrippedstate.
 44. The system of claim 41, wherein the at least one sensorcondition is indicative of a false alarm based on an order in which atleast two sensors are tripped.
 45. The system of claim 41, wherein thefirst instructions, when executed by the one or more first processors,cause the first computing device to: cause, based on a period of timesince a mobile device, associated with the premises, left the premises,adjusted output of the alarm.
 46. The system of claim 41, wherein thefirst instructions, when executed by the one or more first processors,cause the first computing device to: cause, based on locationinformation of a mobile device associated with the premises, adjustedoutput of the alarm.
 47. The system of claim 41, wherein the firstinstructions, when executed by the one or more first processors, causethe first computing device to: based on the determining that the alarmat the premises is a false alarm, send messages, indicating the falsealarm, to a plurality of telephone numbers in an order that is indicatedby information associated with a security system at the premises. 48.The system of claim 41, wherein the at least one sensor conditioncomprises at least two sensor conditions.
 49. The method of claim 9,further comprising causing, based on the determining that the alarm atthe premises is a false alarm, adjusted output of the alarm at thepremises.
 50. The method of claim 9, wherein the alarm at the premisescomprises an audible siren.
 51. The apparatus of claim 24, wherein theinstructions, when executed by the one or more processors, further causethe apparatus to: cause, based on the determining that the alarm at thepremises is a false alarm, adjusted output of the alarm at the premises.52. The apparatus of claim 24, wherein the alarm at the premisescomprises an audible siren.
 53. The non-transitory computer-readablemedium of claim 33, wherein the instructions, when executed, furthercause, based on the determining that the alarm at the premises is afalse alarm, adjusted output of the alarm at the premises.
 54. Thenon-transitory computer-readable medium of claim 33, wherein the alarmat the premises comprises an audible siren.
 55. The system of claim 41,wherein the first instructions, when executed by the one or more firstprocessors, further cause the first computing device to: cause, based onthe determining that the alarm at the premises is a false alarm,adjusted output of the alarm at the premises.
 56. The system of claim41, wherein the alarm at the premises comprises an audible siren.
 57. Anon-transitory computer-readable medium storing instructions that, whenexecuted, cause: receiving an indication of an alarm triggering event ata premises; based on receiving the indication of the alarm triggeringevent, determining at least one sensor condition, wherein the at leastone sensor condition is associated with at least one sensor of thepremises; and determining, based on the at least one sensor conditionand information indicating a false alarm, that an alarm at the premisesassociated with the alarm triggering event is a false alarm.
 58. Thenon-transitory computer-readable medium of claim 57, wherein theinstructions, when executed, further cause, based on the determiningthat the alarm at the premises is a false alarm, performing at least oneof the following: deactivating the alarm; extending an abort windowassociated with the alarm; determining a contact method for sending amessage indicating the false alarm; confirming a status of the at leastone sensor; or causing adjustment of a countdown timer associated withthe alarm.
 59. The non-transitory computer-readable medium of claim 57,wherein the at least one sensor is associated with a doorway.
 60. Thenon-transitory computer-readable medium of claim 57, wherein the atleast one sensor condition indicates that a first door sensor is in atripped state and that a second door sensor is in an untripped state.61. The non-transitory computer-readable medium of claim 57, wherein theinstructions, when executed, further cause: causing, based on a periodof time since a mobile device, associated with the premises, left thepremises, adjusted output of the alarm.
 62. The non-transitorycomputer-readable medium of claim 57, wherein the instructions, whenexecuted, further cause: causing, based on location information of amobile device associated with the premises, adjusted output of thealarm.
 63. The non-transitory computer-readable medium of claim 57,wherein the at least one sensor comprises at least one of: a doorsensor; a floor motion sensor; or a glass break sensor.
 64. Thenon-transitory computer-readable medium of claim 57, wherein theinstructions, when executed, further cause: receiving current locationinformation of a user device; and sending, to the user device and basedon the current location information of the user device, a messageindicating that the alarm is a false alarm.
 65. A system comprising: afirst computing device comprising: one or more first processors; andfirst memory storing first instructions that, when executed by the oneor more first processors, cause the first computing device to: receivean indication of an alarm triggering event at a premises; based onreceiving the indication of the alarm triggering event, determine atleast one sensor condition, wherein the at least one sensor condition isassociated with at least one sensor of the premises; and determine,based on the at least one sensor condition and information indicating afalse alarm, that an alarm at the premises associated with the alarmtriggering event is a false alarm; a second computing device comprising:one or more second processors; and second memory storing secondinstructions that, when executed by the one or more second processors,cause the second computing device to: send the indication of the alarmtriggering event at the premises.
 66. The system of claim 65, whereinthe first instructions, when executed by the one or more firstprocessors, further cause the first computing device to: based on thedetermining that the alarm at the premises is a false alarm, perform atleast one of the following: deactivating the alarm; extending an abortwindow associated with the alarm; determining a contact method forsending a message indicating the false alarm; confirming a status of theat least one sensor; or causing adjustment of a countdown timerassociated with the alarm.
 67. The system of claim 65, wherein the atleast one sensor is associated with a doorway.
 68. The system of claim65, wherein the at least one sensor condition indicates that a firstdoor sensor is in a tripped state and that a second door sensor is in anuntripped state.
 69. The system of claim 65, wherein the firstinstructions, when executed by the one or more first processors, furthercause the first computing device to: cause, based on a period of timesince a mobile device, associated with the premises, left the premises,adjusted output of the alarm.
 70. The system of claim 65, wherein thefirst instructions, when executed by the one or more first processors,further cause the first computing device to: cause, based on locationinformation of a mobile device associated with the premises, adjustedoutput of the alarm.
 71. The system of claim 65, wherein the at leastone sensor comprises at least one of: a door sensor; a floor motionsensor; or a glass break sensor.
 72. The system of claim 65, wherein thefirst instructions, when executed by the one or more first processors,further cause the first computing device to: receive current locationinformation of a user device; and send, to the user device and based onthe current location information of the user device, a messageindicating that the alarm is a false alarm.